Paradigm(s) | multi-paradigm: imperative, object-oriented, functional, meta |
---|---|
Appeared in | 1999 |
Designed by | Walter Bright |
Developer | Digital Mars |
Stable release |
2.057 (December 13, 2011[1]) |
Typing discipline | strong, static |
Major implementations | DMD (reference implementation), GDC, LDC |
Influenced by | C, C++, C#, Java, Eiffel, Python, Ruby |
Influenced | MiniD, DScript, Vala, Qore |
OS | DMD: Unix-like, Windows, Mac OS X |
License | GPL (DMD frontend), Boost (standard and runtime libraries), Source-available (DMD backend), Fully open-source (LDC and GDC)[3] |
Usual filename extensions | .d |
Website | www.d-programming-language.org |
D Programming at Wikibooks |
The D programming language is an object-oriented, imperative, multi-paradigm system programming language created by Walter Bright of Digital Mars. It originated as a re-engineering of C++, but even though it is mainly influenced by that language, it is not a variant of C++. D has redesigned some C++ features and has been influenced by concepts used in other programming languages, such as Java, Python, Ruby, C#, and Eiffel.
D's design goals attempt to combine the performance of compiled languages with the safety and expressive power of modern dynamic languages. Idiomatic D code is commonly as fast as equivalent C++ code, while being shorter and memory-safe. Type inference, automatic memory management and syntax sugar for common types allow faster development, while bounds checking, Design by contract features and a concurrency-aware type system help reduce the occurrence of bugs.[4]
Contents |
D is designed with lessons learned from practical C++ usage rather than from a theoretical perspective. Even though it uses many C/C++ concepts it also discards some, and as such is not compatible with C/C++ source code. It adds to the functionality of C++ by also implementing design by contract, unit testing, true modules, garbage collection, first class arrays, associative arrays, dynamic arrays, array slicing, nested functions, inner classes, closures, anonymous functions, compile time function execution, lazy evaluation and has a reengineered template syntax. D retains C++'s ability to do low-level coding, and adds to it with support for an integrated inline assembler. C++ multiple inheritance is replaced by Java style single inheritance with interfaces and mixins. D's declaration, statement and expression syntax closely matches that of C++.
The inline assembler typifies the differences between D and application languages like Java and C#. An inline assembler lets programmers enter machine-specific assembly code within standard D code, a method often used by system programmers to access the low-level features of the processor needed to run programs that interface directly with the underlying hardware, such as operating systems and device drivers.
D has built-in support for documentation comments, allowing automatic documentation generation.
D supports five main programming paradigms—imperative, object-oriented, metaprogramming, functional and concurrent (Actor model).
Imperative programming in D is almost identical to C. Functions, data, statements, declarations and expressions work just as in C, and the C runtime library can be accessed directly. Some notable differences between D and C in the area of imperative programming include D's foreach
loop construct, which allows looping over a collection, and nested functions, which are functions that are declared inside of another and may access the enclosing function's local variables.
Object-oriented programming in D is based on a single inheritance hierarchy, with all classes derived from class Object. D does not support multiple inheritance; instead, it uses Java-style interfaces, which are comparable to C++ pure abstract classes, and mixins, which allow separating common functionality out of the inheritance hierarchy. D also allows declaring static and final (non-virtual) methods in interfaces.
Metaprogramming is supported by a combination of templates, compile time function execution, tuples, and string mixins. The following examples demonstrate some of D's compile-time features.
Templates in D can be written in a more function-like style than those in C++. This is a regular function that calculates the factorial of a number:
ulong factorial(ulong n) { if(n < 2) return 1; else return n * factorial(n - 1); }
Here, the use of static if
, D's compile-time conditional construct, is demonstrated to construct a template that performs the same calculation using code that is similar to that of the above function:
template Factorial(ulong n) { static if(n < 2) const Factorial = 1; else const Factorial = n * Factorial!(n - 1); }
In the following two examples, the template and function defined above are used to compute factorials. The types of constants need not be specified explicitly as the compiler infers their types from the right-hand sides of assignments:
const fact_7 = Factorial!(7);
This is an example of compile time function execution. Ordinary functions may be used in constant, compile-time expressions provided they meet certain criteria:
const fact_9 = factorial(9);
The std.metastrings.Format
template performs printf
-like data formatting, and the "msg" pragma displays the result at compile time:
import std.metastrings; pragma(msg, Format!("7! = %s", fact_7)); pragma(msg, Format!("9! = %s", fact_9));
String mixins, combined with compile-time function execution, allow generating D code using string operations at compile time. This can be used to parse domain-specific languages to D code, which will be compiled as part of the program:
import FooToD; // hypothetical module which contains a function that parses Foo source code // and returns equivalent D code void main() { mixin(fooToD(import("example.foo"))); }
import std.algorithm, std.range, std.stdio; void main() { int[] a1 = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]; int[] a2 = [6, 7, 8, 9]; // must be immutable to allow access from inside mySum immutable pivot = 5; int mySum(int a, int b) pure nothrow // pure function { if (b <= pivot) // ref to enclosing-scope return a + b; else return a; } // passing a delegate (closure) auto result = reduce!mySum(chain(a1, a2)); writeln("Result: ", result); // output is "15" }
import std.concurrency, std.stdio, std.typecons; int main() { auto tid = spawn(&foo); // spawn a new thread running foo() foreach(i; 0 .. 10) tid.send(i); // send some integers tid.send(1.0f); // send a float tid.send("hello"); // send a string tid.send(thisTid); // send a struct (Tid) receive( (int x) { writeln("Main thread received message: ", x); } ); return 0; } void foo() { bool cont = true; while (cont) { receive( // delegates are used to match the message type (int msg) { writeln("int received: ", msg); }, (Tid sender) { cont = false; sender.send(-1); }, (Variant v) { writeln("huh?"); } // Variant matches any type ); } }
Memory is usually managed with garbage collection, but specific objects can be finalized immediately when they go out of scope. Explicit memory management is possible using the overloaded operators new
and delete
, and by simply calling C's malloc and free directly. Garbage collection can be controlled: programmers can add and exclude memory ranges from being observed by the collector, can disable and enable the collector and force a generational or a full collection cycle.[5] The manual gives many examples of how to implement different highly optimized memory management schemes for when garbage collection is inadequate in a program.
C's application binary interface (ABI) is supported as well as all of C's fundamental and derived types, enabling direct access to existing C code and libraries. D bindings are available for many popular C libraries. C's standard library is part of standard D.
C++'s ABI is not fully supported, although D can access C++ code that is written to the C ABI. The D parser understands an extern (C++) calling convention for limited linking to C++ objects.
On Microsoft Windows, D can access Component Object Model (COM) code.
D was first released in 2001[6], and reached version 1.0 in January 2007. The first version of the language (D1) concentrated on the imperative, object oriented and metaprogramming paradigms[7], similar to C++.
Dissatisfied with Phobos, D's official runtime and standard library, members of the D community created an alternative runtime and standard library named Tango. The first public Tango announcement coincided within days of D 1.0's release.[8] Tango adopted a different programming style, embracing OOP and high modularity. Being a community-led project, Tango was more open to contributions, which allowed it to progress faster than the official standard library. At that time, Tango and Phobos were incompatible due to different runtime support APIs (the garbage collector, threading support, etc.). This made it impossible to use both libraries in the same project. The existence of two libraries, both widely in use, has led to significant dispute due to some packages using Phobos and others using Tango.[9]
In June 2007, the first version of D2 was released. The beginning of D2's development signalled the stabilization of D1; the first version of the language has since been in maintenance, only receiving corrections and implementation bugfixes. D2 was to introduce breaking changes to the language, beginning with its first experimental const system. D2 later added numerous other language features, such as closures, purity, and support for the functional and concurrent programming paradigms. D2 also solved standard library problems by separating the runtime from the standard library, although no official port of Tango for D2 exists today.
The release of Andrei Alexandrescu's book The D Programming Language on June 12, 2010 marked the stabilization of D2, which today is commonly referred to as just "D".
In January 2011, D development moved from a bugtracker / patch-submission basis to GitHub. This has led to a significant increase in contributions to the compiler, runtime and standard library.[10]
Most current D implementations compile directly into machine code for efficient execution.
Editors and integrated development environments (IDEs) supporting D include Eclipse, Microsoft Visual Studio, SlickEdit, Emacs, vim, SciTE, Smultron, TextMate, Zeus,[16] and Geany among others.[17]
Open source D IDEs for Windows exist, some written in D, such as Poseidon,[22] D-IDE,[23] and Entice Designer.[24]
D applications can be debugged using any C/C++ debugger, like GDB or WinDbg, although support for various D-specific language features is extremely limited. On Windows, D programs can be debugged using Ddbg, or Microsoft debugging tools (WinDBG and Visual Studio), after having converted the debug information using cv2pdb. The ZeroBUGS debugger for Linux has experimental support for the D language. Ddbg can be used with various IDEs or from the command line; ZeroBUGS has its own graphical user interface (GUI).
This example program prints its command line arguments. The main
function is the entry point of a D program, and args
is an array of strings representing the command line arguments. A string
in D is an array of characters, represented by char[]
in D1, or immutable(char)[]
in D2.
import std.stdio: writefln; void main(string[] args) { foreach (i, arg; args) writefln("args[%d] = '%s'", i, arg); }
The foreach
statement can iterate over any collection, in this case it is producing a sequence of indexes (i
) and values (arg
) from the array args
. The index i
and the value arg
have their types inferred from the type of the array args
.
The following shows several D capabilities and D design trade-offs in a very short program. It iterates the lines of a text file named words.txt
that contains a different word on each line, and prints all the words that are anagrams of other words.
import std.stdio, std.algorithm, std.range, std.string; void main() { dstring[][dstring] signs2words; foreach (dchar[] w; lines(File("words.txt"))) { immutable key = w.chomp().toLower().sort().release().idup; signs2words[key] ~= w.chomp().idup; } foreach (words; signs2words) if (words.length > 1) writefln(words.join(" ")); }
signs2words
is a built-in associative array that maps dstring (32-bit / char) keys to arrays of dstrings. It is similar to defaultdict(list)
in Python.lines(File())
yields lines lazily, with the newline. It has to then be copied with idup
to obtain a string to be used for the associative array values (the idup
property of arrays returns an immutable duplicate of the array, which is required since the dstring
type is actually immutable(dchar)[]
). Built-in associative arrays require immutable keys.~=
operator appends a new dstring to the values of the associate dynamic array.toLower
, join
and chomp
are string functions that D allows to use with a method syntax. The name of such functions is often very similar to Python string methods. The toLower
converts a string to lower case, join(" ")
joins an array of strings into a single string using a single space as separator, and chomp removes the eventually present newline from the end of the string.sort
is an std.algorithm function that sorts the array in place, creating a unique signature for words that are anagrams of each other. The release() method of sort() is handy to keep the code as a single expression.foreach
iterates on the values of the associative array, it's able to infer the type of words
.key
is assigned to an immutable variable, its type is inferred.
|